Skip to content

Conversation

@monkey92t
Copy link
Collaborator

@monkey92t monkey92t commented Apr 5, 2023

This is the first step for us to implement client-side caching, although no functionality has been implemented yet. 😄

Signed-off-by: monkey92t <golang@88.com>
@monkey92t monkey92t changed the title feat: cache init feat: side-client caching Apr 5, 2023
@monkey92t monkey92t changed the title feat: side-client caching feat: client-side caching Apr 5, 2023
@monkey92t monkey92t marked this pull request as draft April 5, 2023 15:53
Signed-off-by: monkey92t <golang@88.com>
@jamalcole
Copy link

This is the first step for us to implement client-side caching, although no functionality has been implemented yet. 😄

@monkey92t any timeline for implementing client side redis? Also, would you like any help on getting this feature implemented?

@monkey92t
Copy link
Collaborator Author

@jamalcole Without a timetable, it is currently still in the testing phase. If you are interested, you can suggest any ideas or code.

@someview
Copy link

Is there some progress about client side cache?

@monkey92t
Copy link
Collaborator Author

Is there some progress about client side cache?

Sorry, I've tried many API designs, but none of them seem to cover all scenarios. I feel like it might be better to develop it based on specific use cases rather than designing a generic API.

@someview
Copy link

someview commented Jun 5, 2024

Is there some progress about client side cache?

Sorry, I've tried many API designs, but none of them seem to cover all scenarios. I feel like it might be better to develop it based on specific use cases rather than designing a generic API.

I find another redis client lib to achieve some client side cache feature. rueidis may offer some feature about this

@ndyakov
Copy link
Member

ndyakov commented Sep 2, 2025

@htemelski-redis will work on this on in a new branch based on master. Closing this PR as stale. @monkey92t let me know if you would like to sync with @htemelski-redis so he can include your work where possible and acknowledge your contributions.

@ndyakov ndyakov closed this Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants